Repository navigation
Prepare Web qualification for llama.cpp v0.9.0 - #212
Merged
Merged
Conversation
Move the exact-upstream CI lane from v0.7.0 to v0.9.0 (cd959bae), matching published llamadart-native v0.9.0, so the bridge source is built and smoked against the upstream the next release candidate will use. The development pin and release workflows are unchanged; the bridge source needs no change.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Move the exact-upstream CI lane from llama.cpp v0.7.0 to v0.9.0 (
cd959bae99ff4bed22bef2604f45241c09bbb8c8), the upstream of published llamadart-native v0.9.0. The bridge source needs no change.llama_cpp.version(v0.5.0) and the release workflows are unchanged: release candidates take upstream identity from their dispatch inputs. Evidence is indocs/v090_qualification.md.Why
Bridge assets v0.1.82 embed llama.cpp v0.8.0, while llamadart 0.19.0 pins native v0.9.0 (llamadart#1786). This puts v0.9.0 under CI before cutting v0.1.83.
cmake/embedding_mode_reserve.cmakestays inactive.mtmd_helper_gen_audio_inp::voice; the bridge TTS path never set it.Tests
Local, Emscripten 6.0.8, Node 24, Playwright Chromium on macOS arm64, clean v0.9.0 checkout:
npm run check:js/npm testverify_ci_reliability.mjs, actionlint,git diff --checkIndependent review: no blocking findings. Its non-blocking note (clone-step lane comparison was unpinned) is fixed in
tests/ci/ci_scope_test.mjs.Remaining release steps (owner approval required)
After merge, dispatch from
mainper CONTRIBUTING.md "Publish Process", correlation idmanual-v0.1.83:bridge_candidate.yml→bridge_qualification.yml→publish_assets.yml(publish_approved=true), with nativev0.9.0, upstreamv0.9.0/cd959bae…, native manifest SHA-2560d2119cdcf34d347a96a996423094498de3393026efb6ad1a96ba286b621c39e,release_tag=v0.1.83,release_rebuild=0. Then llamadart adopts v0.1.83.